[Conflicts] DNM: Update aws-pcluster-amazonlinux-2 stacks#293
[Conflicts] DNM: Update aws-pcluster-amazonlinux-2 stacks#293lrbison wants to merge 1 commit intospack:developfrom
Conversation
|
Marking this as draft since I still need to merge and tag the runner and update the references here. Also puzzling: CI for this job claims nothing has changed. This seems like it might be possible since I haven't changed compiler versions, but it also leaves me wondering if I have a working build-process in my runner. |
lrbison
changed the title
These stacks start the build with gcc@12 installed from a local buildcache
bernhardkaindl
left a comment
bernhardkaindl
left a comment
There was a problem hiding this comment.
@lrbison, due to the merge other conflicting changes to context (+/- 3 lines) of some of your changes your branch now conflicting with develop and cannot be merged as-is:
This branch has conflicts that must be resolved
Use the command line to resolve conflicts before continuing.
.ci/gitlab/stacks/aws-pcluster-neoverse_v1/spack.yaml
.ci/gitlab/stacks/aws-pcluster-x86_64_v4/spack.yaml
bernhardkaindl
changed the title
|
This pull request has been automatically marked as stale because it has not had any activity in the last 6 months. It will be closed in 30 days if there is no further activity. |
2 participants
Update the aws-pcluster-amazonlinux-2 stacks. These stacks will now use an in-image build-cache for intel and gcc compilers. I expect the gcc compiler to be pushed to the public build-cache where users can install directly without using our previous method of hosting a special buildcache on-the-side.
This change made possible by compilers-as-dependencies!
Replaces #83, which wasn't re-building packages like I expected. Fresh PR should help.